Skip to content

feat: automate release flow with GitHub App, per-skill versions, and supabase-plugin dispatch#75

Merged
Rodriguespn merged 4 commits into
mainfrom
feat/release-flow
May 6, 2026
Merged

feat: automate release flow with GitHub App, per-skill versions, and supabase-plugin dispatch#75
Rodriguespn merged 4 commits into
mainfrom
feat/release-flow

Conversation

@Rodriguespn
Copy link
Copy Markdown
Collaborator

@Rodriguespn Rodriguespn commented May 6, 2026

Summary

  • GitHub App for release-please — switches from GITHUB_TOKEN to a GitHub App token (GH_APP_ID / GH_APP_PRIVATE_KEY) so CI workflows run on release PRs, matching the pattern used in supabase-mcp
  • Automatic supabase-plugin sync — after each release, a second GitHub App token (scoped to supabase-community) dispatches the sync-agent-skills workflow in supabase-community/supabase-plugin immediately via workflow_dispatch, instead of waiting for the weekly cron
  • Per-skill version bumps — adds each skill's SKILL.md to release-please-config.json extra-files so metadata.version is bumped automatically on every release; contributors no longer need to bump it manually
  • Updated docsCONTRIBUTING.md and AGENTS.md reflect the accurate end-to-end release flow, include the release-please-config.json registration step for new skills, and add troubleshooting footnotes

Secrets required in supabase/agent-skills

Secret Purpose
GH_APP_ID GitHub App installed on supabase/agent-skills — enables CI on release PRs
GH_APP_PRIVATE_KEY Private key for the above
GH_APP_ID_SUPABASE_PLUGIN GitHub App installed on supabase-community — dispatches sync to supabase-plugin
GH_APP_PRIVATE_KEY_SUPABASE_PLUGIN Private key for the above

All four secrets are already configured.

Closes AI-673

Rodriguespn and others added 4 commits May 6, 2026 17:02
- Switch release-please to use GitHub App token (GH_APP_ID / GH_APP_PRIVATE_KEY)
  so CI runs on release PRs, matching the pattern used in supabase-mcp
- Add a second GitHub App token step scoped to supabase-community to dispatch
  the sync-agent-skills workflow in supabase-plugin immediately after each release
- Add per-skill SKILL.md metadata.version bumps to release-please-config.json
  extra-files so skill versions are kept in sync automatically on every release

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
- Remove stale instruction to manually bump metadata.version (now automated)
- Document end-to-end release flow: conventional commit → Release Please PR →
  GitHub release → tarballs → supabase-plugin dispatch
- Add release-please-config.json registration step for new skills with the
  required extra-files JSON snippet
- Add troubleshooting footnotes for bad-state Release Please PRs and missed
  supabase-plugin dispatches

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@Rodriguespn Rodriguespn force-pushed the feat/release-flow branch from ecece1d to 47a367f Compare May 6, 2026 14:03
@Rodriguespn Rodriguespn self-assigned this May 6, 2026
@Rodriguespn Rodriguespn merged commit 27838be into main May 6, 2026
1 check passed
@Rodriguespn Rodriguespn deleted the feat/release-flow branch May 6, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant